home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Aminet 4
/
Aminet 4 - November 1994.iso
/
aminet
/
comm
/
net
/
dnet_src.lha
/
dnet
/
amiga
/
doc
/
dnet.doc
< prev
next >
Wrap
Text File
|
1990-12-13
|
7KB
|
200 lines
AMIGA-DNET V2.20
AMIGA CONFIGURATION
ENV: must be assigned and writable.
S:DNET.CONFIG contains configuration info for DNet
S:DNET.SERVERS contains the server list for dnet (and paths to
the server executables)
Any DNet clients you wish to run or have DNet run must be in your path.
(i.e. FTERM, PUTFILES, GETFILES ...)
Other files will be required if you intend to run DNet *as* a BBS.
DNET OPTIONS
(please refer to S:DNET.CONFIG while reading this)
DNet runs in three basic modes: AutoAnswer (-a), DialOut (default),
and Manual (-X). Each mode has its own default set of security
parameters. The shipped defaults assume a hostile enviroment.
Generally, AutoAnswer is assumed to be the most hostile since you
do not know who is calling you up. DialOut is less so since you know
who you are dialing, and Manual assumes a non-hostile enviroment.
These three modes also cause DNet to work differently.
AMIGA/DNET
DialOutMode:
The default mode is DialOutMode (neither -X or -a given).
DNet will look for a CONNECT message on carrier detect and
modify the baud rate according to the AUTA resources.
DNet will set the security modes to the ENVO (originate)
resources in s:dnet.config
NOTE: response through the initial window will be slow due
to DNet's scanning of the resource file s:dnet.config.
-X Manual mode. DNet will look for a CONNECT message on
carrier detect and modify the baud rate on connect
appropriately.
DNet will set the security modes to the ENVM resources
which assumes a friendly connection.
-a Auto Answer mode. DNet will send the RESM resources at
the originally specified baud rate to reset the modem
whenever carrier is lost.
The security modes are set the the ENVA resources, which
normally assume a hostile enviroment.
-8 Use 8 bits no parity for the initial window rather than
7 bits even parity. NOTE! This only effects the initial
login window. The Protocol, when running, always uses
8 bits no parity.
-bbaud Set Initial Baud rate (otherwise uses preferences baud
rate)
-Bbaud Set Baud used to determine timeouts. If not set, the
current baud rate, whatever that is, is used. If set,
this value is used to calculate timeouts forever after
no matter what the actual line baud rate is.
For example, setting this value lower than whatever baud
rate you normally use will allow for longer line delays
(such as when dialing through networks and things)
-sclient Run the specified client program on protocol start. If
running a BBS you want to specify the BBS client program
here.
NOTE: If the DNET_NORUNCLIENT enviroment variable is set,
no client program will be run even if this option is
specified.
The default is to run the FTERM client.
-nhostname Set the hostname (not used)
-h1 Enable Carrier checking. Default is to not check the CD
line (reversed from earlier versions). Note that carrier
checking is forced if you use -a (auto answer) mode.
-U# Set the unit number for the low level serial-like device
to talk over.
-Ddevice Set the device name for the low level serial-like device
to talk over (i.e. "serial.device").
-N# Set the network ID for local client/server rendezvous
-p Packet Debug mode
-d Debug mode on
-m0 Select 8 bit packet mode (default is -m1 which selects
7 bit packet mode)
Note that packets containing binary data will be aproximately
25% larger in 7 bit mode. Packets containing ascii data will
be normal-sized.
In 8 bit mode, simple compression may actually occur... packets
containing all ascii data 0x00-0x7F will be compressed to make
use of the 8th bit which would normally be 0, giving an
aproximately 1/8 speed increase.
-Pn n = 0 none
1 xon-xoff
2 7wire
if -P not specified then the preferences protocol is used.
-Zn n = 0 8-no parity
1 7-odd
2 7-even
3 7-mark
4 7-space
if no -Z option is specified the preferences parity and
wordlength is used.
WARNING: You CANNOT combine xon/xoff *and* -m0.
---------------------------------------------------
SECURITY
The following enviroment variables should exist:
DNET_LEVEL, DNET_READ, DNET_WRITE, DNET_GROUP, DNET_USERID
These are setup automatically by the S:dnet.config file depending on
the mode (Manual, DialOut (-X), AutoAnswer (-a)) and are read by local
servers to determine what the remote machine is allowed to do. These
variables each hold a single value, normally 0-9 (except for DNET_GROUP
which can be any number 0-32767).
SGCOPY (server for getfiles):
This is a new server.
DNET_READ and DNET_GROUP determine which files the remote machine may download
(read). In order for the remote to be able to download a file,
that file and all its parent directories are scanned. At least
one comment field must have an AC entry (AC=n) less than or
equal to the current DNET_READ enviroment variable or sgcopy will
disallow the download. If NO comment fields have an AC entry
the download is disallowed. If any comment field has an AC
entry > DNET_READ, the download is disallowed unless a GP entry
was found (GR=n).
A comment field may have multiple GR entries (GR=n GR=n ...). If
any matches DNET_GROUP and all (if any) AC fields are <= DNET_READ,
the download is allowed.
After that point a download will begin and files/dirs need not have
AC entries. However, if any do, it will be checked again DNET_READ
and the download (for that file or directory) disallowed.
SCOPY (server for putfiles)
This server allows remote machines to upload a file. That is,
transfer from the remote machine to the local machine. DNET_WRITE
must be 9 or higher or the upload will be disallowed. Currently,
the remote machine may upload anywhere so it is suggested that you
either NOT have the SCOPY server installed or do not set DNET_WRITE
to 9 or beyond when talking to possibly hostile remote machines.
SPRINT (printer server)
This server copies a stream to PRT: DNET_WRITE must be at least
6 or the remote machine will not be allowed to use this server.
SCLI (CLI server)
This server is currently a big hack and requires a special pipe
device to work (The 1.3 pipe: will not work).
DNET_LEVEL must be at least 9 for a remote machine to be able to
start a remote cli
STERM (terminal window server)
This server requires no permissions to operate and allows the
remote machine to bring up a 'terminal window' to talk you
through.
AUTOMATIC ENVIROMENT VARIABLE CONFIGURATION CAN BE DONE FROM
S:DNET.CONFIG